Add broker readiness notification channel skeleton#976
Open
wdcui wants to merge 8 commits into
Open
Conversation
Define broker-to-local notification messages and channel traits, including event readiness snapshots, and add Unix-socket framing support for notification traffic. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Extend the userland broker integration test with a real Unix-socket notification path between the broker-side test helper and fake runner. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Replace the standalone notification sender with a broker-stack smoke test that sends readiness for the actual event handle observed through serve_connection. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Set a read timeout on the notification socket so the broker-stack smoke test fails instead of hanging if readiness notification delivery regresses. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Add a production broker-host entry point that serves control requests with a paired notification channel and emits readiness notifications for state-changing event requests. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Remove the private NegotiatedConnection enum and use a small handshake helper that returns an early termination only when negotiation does not reach the active request loop. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Use consistent control-channel naming, document that notification transport stays outside BrokerSession, and inline readiness notification construction in the request loop. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Keep this PR focused on protocol and transport skeleton pieces; defer broker-host notification serving and end-to-end runtime tests until the production semantics are defined. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
wdcui
force-pushed
the
wdcui/ulitebox/broker-readiness-notifications
branch
from
0a008f0 to
b420313
Compare
|
🤖 SemverChecks 🤖 No breaking API changes detected Note: this does not mean API is unchanged, or even that there are no breaking changes; simply, none of the detections triggered. |
github-merge-queue
Bot
removed this pull request from the merge queue due to failed status checks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a minimal broker-to-local notification channel skeleton for readiness updates while keeping the control channel strictly paired request/response. The PR defines event readiness notification DTOs, wire codec coverage, channel traits, and Unix-socket notification send/receive support without changing shim behavior or enabling blocking eventfd yet.